UCF STIG Viewer Logo
Changes are coming to https://stigviewer.com. Take our survey to help us understand your usage and how we can better serve you in the future.
Take Survey

CL/SuperSession Install data sets must be properly protected.


Overview

Finding ID Version Rule ID IA Controls Severity
V-224651 ZCLST000 SV-224651r855142_rule Medium
Description
CL/SuperSession Install data sets provide the capability to use privileged functions and/or have access to sensitive data. Failure to properly restrict access to their data sets could result in violating the integrity of the base product which could result in compromising the operating system or sensitive data.
STIG Date
z/OS CL/SuperSession for TSS Security Technical Implementation Guide 2024-02-19

Details

Check Text ( C-26334r519770_chk )
a) Refer to the following report produced by the Data Set and Resource Data Collection:

- SENSITVE.RPT(KLSRPT)

Automated Analysis:
Refer to the following report produced by the Data Set and Resource Data Collection:

- PDI(ZCLS0000)

b) Verify that access to the CL/SuperSession Install data sets are properly restricted.

___ The TSS data set rules for the data sets does not restrict UPDATE and/or ALTER access to systems programming personnel.

___ The TSS data set rules for the data sets does not specify that all (i.e., failures and successes) UPDATE and/or ALTER access will be logged.

c) If all of the above are untrue, there is NO FINDING.

d) If any of the above is true, this is a FINDING.
Fix Text (F-26322r519771_fix)
Ensure that update and allocate access to CL/SuperSession install data sets are limited to system programmers only, and all update and allocate access is logged.

The installing systems programmer will identify and document the product data sets and categorize them according to who will have update and alter access and if required that all update and allocate access is logged. He will identify if any additional groups have update access for specific data sets, and once documented he will work with the ISSO to see that they are properly restricted to the ACP (Access Control Program ) active on the system.

The following are an example of data sets to be protected:
sys2.omegamon.
sys2.omegamon.*.tlsload
sys2.omegamon.*.tlvload
sys3.omegamon.
sys3.omegamon.rlsload

The following commands are provided as an example for implementing dataset controls:
TSS PERMIT(syspaudt) DSN(sys2.omegamon.) ACCESS(r)
TSS PERMIT(syspaudt) DSN(sys2.omegamon.) ACCESS(all) ACTION(audit)
TSS PERMIT(syspaudt) DSN(sys2.omegamon.*.tlsload) ACCESS(r)
TSS PERMIT(syspaudt) DSN(sys2.omegamon.*.tlsload) ACCESS(all) ACTION(audit)
TSS PERMIT(syspaudt) DSN(sys2.omegamon.*.tlvload) ACCESS(r)
TSS PERMIT(syspaudt) DSN(sys2.omegamon.*.tlvload) ACCESS(all) ACTION(audit)
TSS PERMIT(syspaudt) DSN(sys3.omegamon.) ACCESS(r)
TSS PERMIT(syspaudt) DSN(sys3.omegamon.) ACCESS(all) ACTION(audit)
TSS PERMIT(syspaudt) DSN(sys3.omegamon.*.rlsload) ACCESS(r)
TSS PERMIT(syspaudt) DSN(sys3.omegamon.*.rlsload) ACCESS(all) ACTION(audit)